Network and user behavior based time-shifted mobile data transmission

ABSTRACT

A computer program product for mobile data transmission is provided in the illustrative embodiments. A request for data is received from a mobile device. A determination is made whether a data transmission over a mobile data communication network in response to the request can be delayed, forming a time-shifting determination. A determination is made, responsive to the time-shifting determination being affirmative, a delayed schedule for the data transmission in response to the request such that the data transmission is completed by a deadline. The data is transmitted over the mobile data communication network according to the delayed schedule.

The present application is a DIVISIONAL nonprovisional applicationclaiming the priority of the filing date of the co-pending and commonlyassigned U.S. patent application Ser. No. 13/590,751 (Attorney DocketNo. IN920120065US1), having a similar title, and filed on Aug. 21, 2012.

BACKGROUND

1. Technical Field

The present invention relates generally to a method, system, andcomputer program product for mobile communications. More particularly,the present invention relates to a method, system, and computer programproduct for network and user behavior based time shifted mobile datatransmission.

2. Description of the Related Art

Mobile data communication essentially is data communication using amobile device at least at one end of the data communication. The databeing communicated to or from the mobile device may be voice data, videodata, application data, session management data, or many other types ofdata.

Some mobile data communications are interactive or time-sensitive datacommunications, in other words, synchronous data communications. Forexample, voice data is time sensitive in that the data has to betransmitted to and from a mobile device without perceptible delays,otherwise the voice communication becomes unacceptable. As anotherexample, a banking transaction may be synchronous because a transactionhas to complete within stipulated time and other transactions cannotproceed until a preceding transaction has completed.

Some other mobile data communications are background communications, ornot time sensitive in nature, in other words, asynchronous datacommunications. For example, a file backup operation may occur in thebackground, may be interrupted and restarted over a period withoutaffecting the end result of creating a backup to or from a mobiledevice.

SUMMARY

The illustrative embodiments provide a method, system, and computerprogram product for mobile data transmission. One embodiment receives arequest for data from a mobile device. The embodiment determines, usinga processor and a memory, whether a data transmission over a mobile datacommunication network in response to the request can be delayed, forminga time-shifting determination. The embodiment further determines,responsive to the time-shifting determination being affirmative, adelayed schedule for the data transmission in response to the requestsuch that the data transmission is completed by a deadline. Theembodiment transmits over the mobile data communication network the dataaccording to the delayed schedule.

In another embodiment, determining the delayed schedule further includesdetermining a probability density function (PDF) of network load in themobile data communication network over a period, wherein the PDF ofnetwork load is determined using historical network load data collectedfrom a set of mobile data communication network infrastructurecomponents. The embodiment further includes determining a pattern ofmovement (mobility pattern) of the mobile device during the period. Theembodiment further includes computing a load threshold using the networkload PDF and the mobility pattern, such that transmitting the data onlywhen network load is below the load threshold satisfies the deadline.The embodiment further includes computing a rate of transmissioncorresponding to the load threshold, wherein the delayed schedule isbased on the rate of transmission.

Another embodiment further includes recomputing the load threshold at aset interval, or at an occurrence of an event in the mobile datacommunication network.

In another embodiment, determining the delayed schedule further includesreceiving a plurality of requests from a corresponding plurality ofmobile devices, wherein each request in the plurality of requests has acorresponding deadline, and wherein the request is one of the pluralityof requests and the deadline is one of the plurality of deadlines. Theembodiment further includes arranging the plurality of requests in anorder of shortest deadline to longest deadline. The embodiment furtherincludes determining a pattern of movement (mobility pattern) of themobile device during a period. The embodiment further includesdetermining a PDF of channel quality in the mobile data communicationnetwork over the period, wherein the PDF of channel quality isdetermined using historical channel quality data collected along themobility patterns during the period. The embodiment further includescomputing a signal threshold using the channel quality PDF and themobility pattern, such that transmitting the data only when signalquality to the mobile device exceeds the signal threshold satisfies thedeadline. The embodiment further includes identifying a time slot whenthe signal quality to the mobile device exceeds the signal threshold,wherein the delayed schedule is based on the identified time slot, andwherein the data is transmitted using the time slot. The embodimentfurther includes scheduling to transmit second data in response to asecond request in the plurality of requests in a second time slot.

Another embodiment further includes recomputing the signal threshold atone of (i) a set interval, and (ii) at an occurrence of an event in themobile data communication network.

In another embodiment, determining the delayed schedule further includesdetermining a pattern of movement (mobility pattern) of the mobiledevice during a period. The embodiment further includes determining aPDF of channel quality in the mobile data communication network over theperiod, wherein the PDF of channel quality is determined usinghistorical channel quality data collected along the mobility patternsduring the period. The embodiment further includes computing a weightparameter using the channel quality PDF and the mobility pattern. Theembodiment further includes computing, at a data transmission time slot,a product of the weight parameter and a signal quality to the mobiledevice, wherein the delayed schedule uses the data transmission timeslot responsive to the product having highest value amongst a pluralityof products corresponding to a plurality of requests during the datatransmission time slot.

Another embodiment further includes recomputing the weight parameter ata set interval, or at an occurrence of an event in the mobile datacommunication network.

Another embodiment further includes determining whether the network loadexceeds a load threshold, wherein the data transmission in response tothe request is not delayed responsive to the time-shifting determinationbeing negative, or the network load not exceeding the load threshold.

Another embodiment further includes sending a set of deadlines and acorresponding set of incentives to the mobile device. The embodimentfurther includes receiving a selection of the deadline from the set ofdeadlines, wherein the deadline delivers a corresponding incentive fromthe set of incentives to the mobile device during the data transmission.

In another embodiment, the corresponding incentive is an improved userexperience in consuming data of the data transmission.

In another embodiment, the corresponding incentive is an improvedquality of service (QoS) during the data transmission.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The novel features believed characteristic of the invention are setforth in the appended claims. The invention itself, however, as well asa preferred mode of use, further objectives and advantages thereof, willbest be understood by reference to the following detailed description ofan illustrative embodiment when read in conjunction with theaccompanying drawings, wherein:

FIG. 1 depicts a pictorial representation of a network of dataprocessing systems in which illustrative embodiments may be implemented;

FIG. 2 depicts a block diagram of a data processing system in whichillustrative embodiments may be implemented;

FIG. 3 depicts an example network load probability density functiongraph that is usable in an illustrative embodiment;

FIG. 4 depicts some example cases of time-shifting data transmissions inaccordance with an illustrative embodiment;

FIG. 5 depicts a block diagram of an example configuration for networkand user behavior based time shifted mobile data transmission inaccordance with an illustrative embodiment;

FIG. 6 depicts a block diagram of a process of network and user behaviorbased time shifted mobile data transmission in accordance with anillustrative embodiment;

FIG. 7 depicts a flowchart of an example process of load threshold basedtime-shifting of data transmission in accordance with an illustrativeembodiment;

FIG. 8 depicts a flowchart of an example process of signal qualitythreshold based time-shifting of data transmission in accordance with anillustrative embodiment; and

FIG. 9 depicts a flowchart of an example process of weight parameterbased time-shifting of data transmission in accordance with anillustrative embodiment.

DETAILED DESCRIPTION

An explosive growth in mobile data traffic is occurring given the rapidadoption of mobile devices such as smartphones, tablet computers, andembedded mobile computing platforms. The mobile data traffic includesmobile data communications for applications such as audio, video, andgaming applications, that are time-sensitive and require near-real-timequality of service (QoS).

The illustrative embodiments recognize that mobile traffic exhibits adistinct diurnal pattern in aggregate network load. For example, themobile data traffic volume varies greatly between peak and off-peaktimes. The illustrative embodiments recognize that at peak load times,the performance of mobile applications degrades uniformly, i.e., whenthe mobile network is experiencing higher than threshold loads, alltypes of mobile data communications suffer from the scarcity ofbandwidth. For example, mobile services consumers are all too familiarwith video lags, choppy voice communications, call drops, slow webpageloads, and transaction timeouts during peak hours designated by themobile carriers.

Network upgrades, capacity increases, or additional spectrum purchaseare cost-prohibitive answers to the explosive demand in mobile datacommunications. Provisioning for peak usage is expensive and results inpoor utilization during off-peak periods. Mobile communication networkoperators are under pressure the make the most of the available networkinfrastructure and wireless spectrum to meet the demand in asatisfactory manner. The illustrative embodiments recognize thatreducing peak load is key to improving mobile data communicationexperience without performing expensive network upgrades.

The illustrative embodiments used to describe the invention generallyaddress and solve the above-described problems and other problemsrelated to providing mobile data communications. The illustrativeembodiments provide a method, system, and computer program product fornetwork and user behavior based time shifted mobile data transmission.

Mobility pattern is a record of a mobile device's position over aperiod. An embodiment uses a mobile data requestor's future positions—atrajectory—using mobility patterns of the mobile device associated withthe requestor. A requestor can be a user of the mobile device or anapplication executing on the mobile device.

Channel quality is a record of an indicator of quality of mobile datacommunication channel that existed between a base-station and a mobiledevice over a period. Signal strength is one example indicator ofchannel quality. Noise to signal ratio is another example of suchindicator. Many other indicators will be conceivable from thisdisclosure by those of ordinary skill in the art and the same arecontemplated within the scope of the illustrative embodiments.

The illustrative embodiments recognize that mobile data consumerspresent predictable mobility patterns with corresponding patterns inchannel quality variation. The illustrative embodiments recognize thatsome requestors are either inherently tolerant to data transmissiondelay, or can be made to behave as such by providing incentives. Forexample, requestors requesting predictable traffic like news-videos,podcasts, sync services, Software upgrades, and large file transfers canbe incentivized with better QoS for time-shifted transmission of therequested data.

An embodiment selects certain mobile data transmissions to a mobiledevice for time-shifting. Time-shifting is the process of delaying orshifting a transmission time for a part of a selected data transmissionto a mobile device. For example, delay-sensitive mobile data traffic,such as video-on-demand, consumes more resources than an equivalent filetransfer of similar size. An embodiment attempts to time-shiftresource-expensive traffic to help alleviate network peak load.

An embodiment provides improved performance as an incentive to acceptingtime-shifted delivery of requested data. For example, an application mayrequest a video-on-demand during peak load time. If the datacommunication continues to provide the video-on-demand service at thattime, the video experience is likely to suffer from buffering delays andinterruptions. On the other hand, if the video-on-demand service ispostponed, or time-shifted, for another time, such as an off-peak time,or when the user has traveled into an area of less than peak load, theuser has the incentive of a better video experience at the cost of adelaying that experience.

Generally, an embodiment matches time-elastic mobile data demand withvarying network resource availability. In other words, an embodimentidentifies delay-tolerant data transmission requests or requestors,negotiates a transmission deadline for the request, for example inexchange for some incentive, and time-shifts the data transmission to alater time when network resources are available above a threshold level.If the data transmission is time-sensitive, an embodiment may negotiatea shorter than a threshold deadline to time-shift the transmission. Ifthe data transmission is not time-sensitive, an embodiment may negotiatea deadline that is longer than a threshold to time-shift thetransmission. Thus, an embodiment achieves network load reduction bytime-shifting data transmissions and delivering the requested data bythe negotiated deadline.

The illustrative embodiments recognize that asking users or mobileapplications repeatedly and during the data demand is impractical. Theillustrative embodiments use statistical analysis of historicalrequestors' usage behavior, historical network load behavior, andhistorical conditions of the mobile data communication channel (channelconditions) for the requestors to devise scheduling strategies that meetdata delivery deadlines.

When an embodiment negotiates a deadline in exchange for performanceincentives, the negotiations can be transparent to the user of themobile device. For example, the user can pre-configure an application tonegotiate a time-shifted deadline for certain type of datatransmissions.

The illustrative embodiments are described with respect to certaindevices only as examples. Such descriptions are not intended to belimiting on the invention. For example, an illustrative embodimentdescribed with respect to a smartphone mobile device can be implementedwith respect to an embedded mobile computing platform in an automobilewithout limitation.

The illustrative embodiments are described with respect to certain dataonly as examples. Such descriptions are not intended to be limiting onthe invention. For example, an illustrative embodiment described withrespect to a smartphone mobile device using video-on-demand can beimplemented with respect to an embedded mobile computing platform in anautomobile requesting map database update within the scope of theillustrative embodiments.

Furthermore, the illustrative embodiments may be implemented withrespect to any type of data, data source, or access to a data sourceover a data network. Any type of data storage device may provide thedata to an embodiment of the invention, either locally at a dataprocessing system or over a data network, within the scope of theinvention.

The illustrative embodiments are described using specific code, designs,architectures, layouts, schematics, and tools only as examples and arenot limiting on the illustrative embodiments. Furthermore, theillustrative embodiments are described in some instances usingparticular software, tools, and data processing environments only as anexample for the clarity of the description. The illustrative embodimentsmay be used in conjunction with other comparable or similarly purposedstructures, systems, applications, or architectures. An illustrativeembodiment may be implemented in hardware, software, or a combinationthereof.

The examples in this disclosure are used only for the clarity of thedescription and are not limiting on the illustrative embodiments.Additional data, operations, actions, tasks, activities, andmanipulations will be conceivable from this disclosure and the same arecontemplated within the scope of the illustrative embodiments.

Any advantages listed herein are only examples and are not intended tobe limiting on the illustrative embodiments. Additional or differentadvantages may be realized by specific illustrative embodiments.Furthermore, a particular illustrative embodiment may have some, all, ornone of the advantages listed above.

With reference to the figures and in particular with reference to FIGS.1 and 2, these figures are example diagrams of data processingenvironments in which illustrative embodiments may be implemented. FIGS.1 and 2 are only examples and are not intended to assert or imply anylimitation with regard to the environments in which differentembodiments may be implemented. A particular implementation may makemany modifications to the depicted environments based on the followingdescription.

FIG. 1 depicts a pictorial representation of a network of dataprocessing systems in which illustrative embodiments may be implemented.Data processing environment 100 is a network of data processing systemsin which the illustrative embodiments may be implemented. Dataprocessing environment 100 includes network 102. Network 102 is themedium used to provide communications links between various devices andcomputers connected together within data processing environment 100.Network 102 may include connections, such as wire, wirelesscommunication links, or fiber optic cables. Server 104 and server 106couple to network 102 along with storage unit 108. Software applicationsmay execute on any data processing system or device in data processingenvironment 100.

Clients 110, 112, and 114 also couple to network 102. A data processingsystem, such as server 104 or 106, or client 110, 112, or 114 maycontain data and may have software applications or software toolsexecuting thereon.

In addition, mobile device 120 may be any suitable mobile dataprocessing system capable of performing mobile data communication usingmobile communications infrastructure, such as, but not limited tobase-station 122. Base-station 122, a wireless access point, a microcell device, a pico cell device, or a femto cell device, or a wirelessantenna are some examples of mobile communication infrastructure thatcan communicate with backend systems, such as server 104, or to anothernetwork via network 102. Application 105 in server 104 implements all orpart an embodiment. In cases where an embodiment is implemented inmultiple modules or components, such modules or components may bedistributed to other data processing systems, such as server 106 orclient 112 (distributed components not shown) in the form of otherapplications. Certain features of an embodiment can be implemented inmobile device 120, base-station 122, server 104, or a combinationthereof, without limitation, and depending on the particularimplementation. Storage 108 includes policies data 123, channel qualitydata (channel quality index, “CQI”) 124, mobility history 125, andnetwork load history 126 for use according to an embodiment. Policiesdata 123, channel quality data (channel quality index, “CQI”) 124,mobility history 125, and network load history 126 may each be stored inany suitable form in storage 108, such as in the form of a database,file, or any other suitable data structure.

In the depicted example, server 104 may provide data, such as bootfiles, operating system images, and applications to clients 110, 112,and 114. Clients 110, 112, and 114 may be clients to server 104 in thisexample. Clients 110, 112, 114, or some combination thereof, may includetheir own data, boot files, operating system images, and applications.Data processing environment 100 may include additional servers, clients,and other devices that are not shown.

Servers 104 and 106, storage unit 108, and clients 110, 112, and 114 maycouple to network 102 using wired connections, wireless communicationprotocols, or other suitable data connectivity. For example, a clustertypically has multiple network types, such as IP networks, directconnections of machines via packets exchange implemented by storageprotocols (Fibre Channel, SCSI), serial links, and message exchange viawriting and reading packets to shared storage such as a hard disk drive.For performance reasons, in sending client traffic, an IP network isgiven precedence. Furthermore, a given network type may not connect toall nodes in a cluster. For instance, a cluster may span machineslocated at two geographically distant sites. For the long distanceconnection, Ethernet may be the preferred connection, and within ageographical location, a direct connection may be preferable.Additionally, within a geographical location, additional non-IPnetworks, such as Fibre channel or serial connections may be used withinthe scope of the illustrative embodiments.

Clients 110, 112, and 114 may be, for example, personal computers,network computers, thin clients, or industrial control systems. In thedepicted example, server 104 may provide data, such as boot files,operating system images, and applications to clients 110, 112, and 114.Clients 110, 112, and 114 may be clients to server 104 in this example.Clients 110, 112, 114, or some combination thereof, may include theirown data, boot files, operating system images, and applications. Dataprocessing environment 100 may include additional servers, clients, andother devices that are not shown.

In the depicted example, data processing environment 100 may be theInternet. Network 102 may represent a collection of networks andgateways that use the Transmission Control Protocol/Internet Protocol(TCP/IP) and other protocols to communicate with one another, andencompasses components including but not limited to IP and SANcomponents. At the heart of the Internet is a backbone of datacommunication links between major nodes or host computers, includingthousands of commercial, governmental, educational, and other computersystems that route data and messages. Of course, data processingenvironment 100 also may be implemented as a number of different typesof networks, such as for example, an intranet, a local area network(LAN), a wide area network (WAN), or mobile ad hoc network (MANET). FIG.1 is intended as an example, and not as an architectural limitation forthe different illustrative embodiments.

Among other uses, data processing environment 100 may be used forimplementing a client-server environment in which the illustrativeembodiments may be implemented. A client-server environment enablessoftware applications and data to be distributed across a network suchthat an application functions by using the interactivity between aclient data processing system and a server data processing system. Dataprocessing environment 100 may also employ a service orientedarchitecture where interoperable software components distributed acrossa network may be packaged together as coherent business applications.

With reference to FIG. 2, this figure depicts a block diagram of a dataprocessing system in which illustrative embodiments may be implemented.Data processing system 200 is an example of a computer, such as server104, server 106, or client 112 in FIG. 1, or another type of device inwhich computer usable program code or instructions implementing theprocesses of the illustrative embodiments may be located for theillustrative embodiments. Data processing system 200 is alsorepresentative of a computing device, such as mobile device 120 in FIG.1 in which computer usable program code or instructions implementing theprocesses of the illustrative embodiments may be located for theillustrative embodiments. Data processing system 200 is alsorepresentative of an embedded mobile computing device, such as a dataprocessing system embedded in a vehicle (not shown) in which computerusable program code or instructions implementing the processes of theillustrative embodiments may be located for the illustrativeembodiments. Data processing system 200 is described as a computer onlyas an example, without being limited thereto. Implementations in theform of mobile device 120 in FIG. 1 may modify data processing system200 and even eliminate certain depicted components there from withoutdeparting from the general description of the operations and functionsof data processing system 200 described herein.

In the depicted example, data processing system 200 employs a hubarchitecture including North Bridge and memory controller hub (NB/MCH)202 and south bridge and input/output (I/O) controller hub (SB/ICH) 204.Processing unit 206, main memory 208, and graphics processor 210 arecoupled to north bridge and memory controller hub (NB/MCH) 202.Processing unit 206 may include one or more processors and may beimplemented using one or more heterogeneous processor systems. Graphicsprocessor 210 may be coupled to NB/MCH 202 through an acceleratedgraphics port (AGP) in certain implementations.

In the depicted example, local area network (LAN) adapter 212 is coupledto south bridge and I/O controller hub (SB/ICH) 204. Audio adapter 216,keyboard and mouse adapter 220, modem 222, read only memory (ROM) 224,universal serial bus (USB) and other ports 232, and PCI/PCIe devices 234are coupled to south bridge and I/O controller hub 204 through bus 238.Hard disk drive (HDD) 226 and CD-ROM 230 are coupled to south bridge andI/O controller hub 204 through bus 240. PCI/PCIe devices 234 mayinclude, for example, Ethernet adapters, add-in cards, and PC cards fornotebook computers. PCI uses a card bus controller, while PCIe does not.ROM 224 may be, for example, a flash binary input/output system (BIOS).Hard disk drive 226 and CD-ROM 230 may use, for example, an integrateddrive electronics (IDE) or serial advanced technology attachment (SATA)interface. A super I/O (SIO) device 236 may be coupled to south bridgeand I/O controller hub (SB/ICH) 204 through bus 238.

An operating system runs on processing unit 206. The operating systemcoordinates and provides control of various components within dataprocessing system 200 in FIG. 2. The operating system may be acommercially available operating system such as Microsoft® Windows®(Microsoft and Windows are trademarks of Microsoft Corporation in theUnited States, other countries, or both), or Linux® (Linux is atrademark of Linus Torvalds in the United States, other countries, orboth). An object oriented programming system, such as the Java™programming system, may run in conjunction with the operating system andprovide calls to the operating system from Java™ programs orapplications executing on data processing system 200 (Java and allJava-based trademarks and logos are trademarks or registered trademarksof Oracle Corporation and/or its affiliates).

Program instructions for the operating system, the object-orientedprogramming system, the processes of the illustrative embodiments, andapplications or programs, including application 105, are located on oneor more storage devices, such as hard disk drive 226 or CD-ROM 230, andmay be loaded into at least one of one or more memories, such as mainmemory 208, read only memory 224, or one or more peripheral devices, forexecution by processing unit 206. Program instructions may also bestored permanently in non-volatile memory and either loaded from thereor executed in place. For example, the synthesized program according toan embodiment can be stored in non-volatile memory and loaded from thereinto DRAM.

The hardware in FIGS. 1-2 may vary depending on the implementation.Other internal hardware or peripheral devices, such as flash memory,equivalent non-volatile memory, or optical disk drives and the like, maybe used in addition to or in place of the hardware depicted in FIGS.1-2. In addition, the processes of the illustrative embodiments may beapplied to a multiprocessor data processing system.

In some illustrative examples, data processing system 200 may be apersonal digital assistant (PDA), which is generally configured withflash memory to provide non-volatile memory for storing operating systemfiles and/or user-generated data. A bus system may comprise one or morebuses, such as a system bus, an I/O bus, and a PCI bus. Of course, thebus system may be implemented using any type of communications fabric orarchitecture that provides for a transfer of data between differentcomponents or devices attached to the fabric or architecture.

A communications unit may include one or more devices used to transmitand receive data, such as a modem or a network adapter. A memory may be,for example, main memory 208 or a cache, such as the cache found innorth bridge and memory controller hub 202. A processing unit mayinclude one or more processors or CPUs.

The depicted examples in FIGS. 1-2 and above-described examples are notmeant to imply architectural limitations. For example, data processingsystem 200 also may be a tablet computer, laptop computer, or telephonedevice in addition to taking the form of a PDA.

With reference to FIG. 3, this figure depicts an example network loadprobability density function graph that is usable in an illustrativeembodiment. Probability density function (PDF) graph 300 can beconstructed using historical data from network load history data 126 instorage 108 in FIG. 1. Graph 300 depicts the load on the X-axis, and theprobability of a value of the load occurring on the Y-axis, over a givenperiod.

With reference to FIG. 4, this figure depicts some example cases oftime-shifting data transmissions in accordance with an illustrativeembodiment. Mobile devices 402 and 404 may be an example of mobiledevice 120 in FIG. 1 at different times. Graphs 412 and 414 areconstructed for projecting network load over different periods usingnetwork load history data 126 in FIG. 1. Period markings are shown atthirty minutes and one hour only as examples for clarity and not as alimitation on an embodiment.

Assume that mobile device 402 has to transfer data of size F and hasagreed to a deadline of one hour. Assume, as shown in graph 412 that attime T1, network load is expected to be lower than threshold 422 for apart of the one-hour negotiated deadline and then exceed threshold 422for the remainder of the period. Accordingly, an embodiment determinesthat the data transmission can be accomplished during time slot 432 asdepicted in graph 412A, which is identical to graph 412.

Similarly, assume that mobile device 404 has to transfer data of size Fand has also agreed to a deadline of one hour. Assume, as shown in graph414 that at time T2, network load is expected to exceed threshold 424for a part of the one-hour negotiated deadline and then reduce belowthreshold 424 for the remainder of the period. Accordingly, anembodiment determines that the data transmission can be accomplishedduring time slot 434 as depicted in graph 414A, which is identical tograph 414.

With reference to FIG. 5, this figure depicts a block diagram of anexample configuration for network and user behavior based time shiftedmobile data transmission in accordance with an illustrative embodiment.Policy module 502, control module 504, and controller 506 can beimplemented as application 105 in FIG. 1. In one embodiment, application105 in FIG. 1 implements one of policy module 502, control module 504,and controller 506, and the remaining modules are each implemented asseparate applications, distributed and executed on data processingsystems in the manner of application 105 on server 104 in FIG. 1.

Policy module 502 accepts data requests from any number of mobiledevices. For example, policy module 502 accepts request 500 from mobiledevice 508, which is i-the requestor amongst n requestors. Mobile device508 is analogous to mobile device 402 or 404 in FIG. 4.

Policy database 510 corresponds to policies data 123 in FIG. 1. Channelquality history database 514 corresponds to CQI data 124 in FIG. 1 andincludes channel quality information collected from mobile devices onthe mobile network. Mobility history database 516 corresponds tomobility history data 125 in FIG. 1 and includes position information,such as location and rate of transition through cells, collected frommobile devices on the mobile network. Network load history database 518corresponds to network load history data 126 in FIG. 1 and includes loaddata collected from network infrastructure components such asbase-stations. Policy database 510, channel quality history database514, mobility history database 516, and network load history database518 are example manifestations of their corresponding counterparts inFIG. 1, without implying a limitation of any particular databasestructure or form.

Policy database 510 provides to policy module 502 one or more policiesor rules to use in computing a time-shifted deadline and a correspondingincentive. Mobility history database 516 provides requestor mobiledevice 508's trajectory. Channel quality history database 514 provideshistorical channel quality information along requestor mobile device508's trajectory. Network load history database 518 provides historicalnetwork load information along requestor mobile device 508's trajectoryduring previous times similar to the time of request 500.

Using the inputs from policy database 510, channel quality historydatabase 514, mobility history database 516, and network load historydatabase 518, policy database module 502 computes one or more sets ofdeadlines and corresponding incentives to offer to mobile device 502.

Using the deadlines and incentives, policy module 502 negotiates 512 adeadline for transmitting the requested data. Mobile device 508 beingthe i-th requestor, policy module 502 sends the negotiated deadlineD_(i) for the requested data size of F_(i) to control module 504. If nodeadline can be negotiated, policy module 502 instructs scheduler 530 inthe mobile network infrastructure to schedule the data transmission ofthe requested data upon request, i.e., serve-on-demand.

Control module 504 includes components for modeling PDFs usinghistorical information. For example, mobility modeler 522 buildspatterns of mobility between cells for a single requestor or a singleclass of requestors at a given time of day using a trajectory learningalgorithm on the data furnished by the mobility history database 516.

Using channel quality history database 514 and mobility history database516, CQI modeler 520 builds statistical models—PDFs—of the wirelesschannel quality seen at a particular location in a given time window.Operating in conjunction with mobility modeler 522, CQI modeler 520builds statistical models of the wireless channel quality along aparticular trajectory, such as the trajectory of mobile device 508.

Load modeler 524 builds statistical models—PDFs—of the load on a givenbase-station at a given time of day, using load history database 518 andmobility database 516. Operating in conjunction with mobility modeler522, load modeler 524 builds statistical models of the load along agiven trajectory, such as the trajectory of mobile device 508.

Using one or more of the PDFs and mobility patterns thus available,control module 504 produces one or more thresholds or parameters,collectively referred to as policy parameters. For example, in oneembodiment, control module 504 produces a signal threshold S_(i) fori-th requestor mobile device 508. In another embodiment, control module504 produces a load threshold L_(i) for i-th requestor mobile device508. In another embodiment, control module 504 produces a weightingparameter W_(i) for i-th requestor mobile device 508. Uses of signalthreshold S_(i), load threshold L_(i), and weighting parameter W_(i) aredescribed in greater detail with respect to FIGS. 7, 8, and 9.

Using one or more policy parameters from control module 504, and presentload conditions at a base-station, such as base-station 122 in FIG. 1,that would be transmitting the requested data, controller 506 produces arate parameter R_(i) for i-th requestor mobile device 508 for request500. Rate parameter Ri is usable by scheduler 530 in the mobile networkinfrastructure to schedule the rate of transmission of the requesteddata from the base-station that would be transmitting the requesteddata.

With reference to FIG. 6, this figure depicts a block diagram of aprocess of network and user behavior based time shifted mobile datatransmission in accordance with an illustrative embodiment. Process 600can be implemented using a combination of policy module 502, controlmodule 504, controller 506, and scheduler 530 in FIG. 5.

Process 600 begins by receiving a data transfer request, such as request500 in FIG. 5, (step 602). Process 600 determines the present networkload at the time of the request is above a threshold level of load (step604). If the network load does not exceed the threshold (“No” path ofstep 604), process 600 serves the request on demand (step 606). As tothe request of step 602, process 600 ends thereafter. Processing arequest on demand when the network load permits allows for the expecteduser-experience and QoS and no deadline negotiations are required.

If the network load exceeds the threshold (“Yes” path of step 604),process 600 determines whether the request of step 602 or a mobiledevice making the request can be time-shifted (step 608). If the requestor the requestor cannot be time-shifted (“No” path of step 608), process600 serves the request on demand at step 606, and ends thereafter as tothe request of step 602.

If the request or the requestor can be time-shifted (“Yes” path of step608), process 600 publishes one or more sets of time-shifted deadlinesand corresponding incentives to the requestor (step 610). Process 600receives a deadline selection (step 612). In one embodiment, anapplication executing in a mobile device may select a deadline in mannertransparent to a user. For example, the application may select adeadline according to a delay tolerance parameter that is preconfiguredaccording to a day, time, type of data, location of the user, or anyother factor. In another embodiment, a user may be prompted to selectone of the deadlines.

Process 600 determines the scheduling, i.e., the rate of transmission,for the transfer of the requested data (step 614). Process 600 schedulesthe data transfer accordingly (step 616). Process 600 ends thereafterfor the request of step 602. In one embodiment, for example owing tonetwork load change, user mobility, or channel quality change, process600 may re-execute for the same request if part of the requested dataremains to be transmitted to the requestor mobile device.

With reference to FIG. 7, this figure depicts a flowchart of an exampleprocess of load threshold based time-shifting of data transmission inaccordance with an illustrative embodiment. Process 700 can beimplemented in control module 504 of FIG. 5 to produce load thresholdL_(i) policy parameter.

Process 700 executes for each requestor i, and begins by receiving adata transfer request for data size F_(i) by deadline D_(i) fromrequestor i (step 702). Process 700 determines a pattern of mobilitybetween cell locations during the period from a present time tilldeadline Di for requestor i (step 704). Process 700 determines a PDF ofnetwork load over a period for requestor i (step 706).

Using the load PDF and the mobility pattern, process 700 computes a loadthreshold L_(i) such that if the data is transmitted to the requestoronly when the network load is less than L_(i), deadline D_(i) is met(step 708).

In each slot, process 700 checks if the load is less than the loadthreshold L_(i), and if so, determines a rate of transmission R_(i)(step 710). At step 708, process 700 recomputes the threshold L_(i) atset intervals or upon certain events using all pending data requests(step 708A), and adjusts rate R_(i) accordingly. Process 700 schedulesthe data transmission according to rate R_(i) (step 712). Process 700ends thereafter.

With reference to FIG. 8, this figure depicts a flowchart of an exampleprocess of signal quality threshold based time-shifting of datatransmission in accordance with an illustrative embodiment. Process 800can be implemented in control module 504 of FIG. 5 to produce signalthreshold S_(i) policy parameter.

Process 800 executes for each requestor i, and begins by receiving adata transfer request for data size F_(i) by deadline D_(i) fromrequestor i (step 802). Process 800 arranges the data transmissionrequests from all active requestors in the order of earliest to latestdeadlines (step 804).

Assume that a requestor index i is initialized to value 1 (step 806).Process 800 calculates the expected fraction of slots occupied byrequestors 1 through i−1 (step 814). Process 800 determines a pattern ofmobility between cell locations during the period for requestor i (step808). Process 800 determines a PDF of channel quality in the unoccupiedslots in the period between a present time and deadline D_(i) forrequestor i (step 810).

For requestor i, using the channel quality PDF and the mobility pattern,process 800 computes a signal threshold S_(i) (a measure of channelquality) such that if the data is transmitted to the requestor only whenthe signal exceed S_(i), deadline D_(i) is met (step 812).

The requestor index i is incremented if more requestors are pending(step 818). If more requestors are pending, process 800 returns to step814 with the incremented index. In another branch of process 800,process 800 also recomputes the signal threshold, such as upon an eventor passage of a set period since the last computed threshold (step 820).For example, process 800 may recompute the threshold L_(i) at setintervals or upon certain events using all pending data requests. Thebranch of process 800 returns to step 804.

If no more requestors are pending, process 800 checks if the load isless than the load threshold L_(i), and if so, determines a rate oftransmission R_(i) (step 830). Process 800 schedules the datatransmission according to rate R_(i) (step 832). Process 800 endsthereafter.

With reference to FIG. 9, this figure depicts a flowchart of an exampleprocess of weight parameter based time-shifting of data transmission inaccordance with an illustrative embodiment. Process 900 can beimplemented in control module 504 of FIG. 5 to produce signal thresholdS_(i) policy parameter.

Process 900 executes for each requestor i. Process 900 receives a datatransfer request for data size F_(i) by deadline D_(i) from requestor i(step 902). Process 900 determines a pattern of mobility between celllocations during the period for requestor i (step 904). Process 900determines a PDF of channel quality over a period from a present timetill deadline Di for requestor i (step 906).

For requestor i, using the PDF and the mobility pattern, process 900computes a weight parameter W_(i) (step 910). At step 910, process 900recomputes the weight parameter W_(i) at set intervals or upon certainevents using all pending data requests (step 910A).

For each transmission slot, process 900 schedules to transmit data forsuch requestor whose product of weight parameter and signal quality isthe highest at the time of the time slot (step 912). Process 900 endsthereafter.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

Thus, a computer implemented method, system, and computer programproduct are provided in the illustrative embodiments for network anduser behavior based time shifted mobile data transmission. Using anembodiment, resource-heavy requests and requests for predictable datatraffic, such as newscasts, can be time-shifted to improve the peak loadbehavior of a mobile network. An embodiment not only improves thenetwork performance of the mobile network during greater than thresholdload times, the embodiment also improves QoS and user-experience duringthe data transmission, although the experience is delayed.

An embodiment can be implemented to operate in conjunction with a radionetwork controller component of mobile network's infrastructure. Anembodiment receives the requests for data transmissions and analyzes therequests to determine whether and how they can be time-shifted. Thetime-shifting of an embodiment operates in conjunction with abase-station scheduler at a coarse-grain time scale of a few seconds toa few minutes.

An embodiment leverages statistical information about channel qualityand network load to devise a schedule that serves each request beforeits specified deadline. An embodiment also minimizes the networkfootprint by varying the rate of feeding the base-station queues so asto opportunistically transmit in periods of low load and high channelquality. An embodiment corrects any errors between prediction based onthe models and real experience during transmission to a mobile device bybootstrapping and recomputing the policy parameters at set intervals orupon certain events.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablestorage device(s) or computer readable media having computer readableprogram code embodied thereon.

Any combination of one or more computer readable storage device(s) orcomputer readable media may be utilized. The computer readable mediummay be a computer readable signal medium or a computer readable storagemedium. A computer readable storage device may be, for example, but notlimited to, an electronic, magnetic, optical, electromagnetic, infrared,or semiconductor system, apparatus, or device, or any suitablecombination of the foregoing. More specific examples (a non-exhaustivelist) of the computer readable storage device would include thefollowing: an electrical connection having one or more wires, a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), an optical fiber, a portable compact disc read-onlymemory (CD-ROM), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage device may be any tangible deviceor medium that can contain, or store a program for use by or inconnection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable storage device or computerreadable medium may be transmitted using any appropriate medium,including but not limited to wireless, wireline, optical fiber cable,RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to one or more processors of one or more general purposecomputers, special purpose computers, or other programmable dataprocessing apparatuses to produce a machine, such that the instructions,which execute via the one or more processors of the computers or otherprogrammable data processing apparatuses, create means for implementingthe functions/acts specified in the flowchart and/or block diagram blockor blocks.

These computer program instructions may also be stored in one or morecomputer readable storage devices or computer readable media that candirect one or more computers, one or more other programmable dataprocessing apparatuses, or one or more other devices to function in aparticular manner, such that the instructions stored in the one or morecomputer readable storage devices or computer readable medium produce anarticle of manufacture including instructions which implement thefunction/act specified in the flowchart and/or block diagram block orblocks.

The computer program instructions may also be loaded onto one or morecomputers, one or more other programmable data processing apparatuses,or one or more other devices to cause a series of operational steps tobe performed on the one or more computers, one or more otherprogrammable data processing apparatuses, or one or more other devicesto produce a computer implemented process such that the instructionswhich execute on the one or more computers, one or more otherprogrammable data processing apparatuses, or one or more other devicesprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiments were chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A computer usable program product comprising acomputer usable storage device including computer usable code for mobiledata transmission, the computer usable code comprising: computer usablecode for receiving a request for data from a mobile device; computerusable code for determining, using a processor and a memory, whether adata transmission over a mobile data communication network in responseto the request can be delayed, forming a time-shifting determination;computer usable code for determining, responsive to the time-shiftingdetermination being affirmative, a delayed schedule for the datatransmission in response to the request such that the data transmissionis completed by a deadline; and computer usable code for transmittingover the mobile data communication network the data according to thedelayed schedule, wherein the computer usable code for determining thedelayed schedule further comprises: computer usable code for receiving aplurality of requests from a corresponding plurality of mobile devices,wherein each request in the plurality of requests has a correspondingdeadline, and wherein the request is one of the plurality of requestsand the deadline is one of the plurality of deadlines; computer usablecode for arranging the plurality of requests in an order of shortestdeadline to longest deadline; computer usable code for determining apattern of movement (mobility pattern) of the mobile device during aperiod; computer usable code for determining a PDF of channel quality inthe mobile data communication network over the period, wherein the PDFof channel quality is determined using historical channel quality datacollected along the mobility patterns during the period; computer usablecode for computing a signal threshold using the channel quality PDF andthe mobility pattern, such that transmitting the data only when signalquality to the mobile device exceeds the signal threshold satisfies thedeadline; computer usable code for identifying a time slot when thesignal quality to the mobile device exceeds the signal threshold,wherein the delayed schedule is based on the identified time slot, andwherein the data is transmitted using the time slot; computer usablecode for scheduling to transmit second data in response to a secondrequest in the plurality of requests in a second time slot.
 2. Thecomputer usable program product of claim 1, further comprising: computerusable code for recomputing the signal threshold at one of (i) a setinterval, and (ii) at an occurrence of an event in the mobile datacommunication network.
 3. A computer usable program product comprising acomputer usable storage device including computer usable code for mobiledata transmission, the computer usable code comprising: computer usablecode for receiving a request for data from a mobile device; computerusable code for determining, using a processor and a memory, whether adata transmission over a mobile data communication network in responseto the request can be delayed, forming a time-shifting determination;computer usable code for determining, responsive to the time-shiftingdetermination being affirmative, a delayed schedule for the datatransmission in response to the request such that the data transmissionis completed by a deadline; and computer usable code for transmittingover the mobile data communication network the data according to thedelayed schedule, wherein the computer usable code for determining thedelayed schedule further comprises: computer usable code for determininga pattern of movement (mobility pattern) of the mobile device during aperiod; computer usable code for determining a PDF of channel quality inthe mobile data communication network over the period, wherein the PDFof channel quality is determined using historical channel quality datacollected along the mobility patterns during the period; computer usablecode for computing a weight parameter using the channel quality PDF andthe mobility pattern; computer usable code for computing, at a datatransmission time slot, a product of the weight parameter and a signalquality to the mobile device, wherein the delayed schedule uses the datatransmission time slot responsive to the product having highest valueamongst a plurality of products corresponding to a plurality of requestsduring the data transmission time slot.
 4. The computer implementedmethod of claim 3, further comprising: recomputing the weight parameterat one of (i) a set interval, and (ii) at an occurrence of an event inthe mobile data communication network.
 25. A data processing system formobile data transmission, the data processing system comprising: astorage device including a storage medium, wherein the storage devicestores computer usable program code; and a processor, wherein theprocessor executes the computer usable program code, and wherein thecomputer usable program code comprises: computer usable code forreceiving a request for data from a mobile device; computer usable codefor determining, using a processor and a memory, whether a datatransmission over a mobile data communication network in response to therequest can be delayed, forming a time-shifting determination; computerusable code for determining, responsive to the time-shiftingdetermination being affirmative, a delayed schedule for the datatransmission in response to the request such that the data transmissionis completed by a deadline; and computer usable code for transmittingover the mobile data communication network the data according to thedelayed schedule.